feature: Added gRPC close signal to Monitor call (allows graceful close of monitor)
          #2276
        
          
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.mdhas been updated with a migration guide (for breaking changes)configuration.schema.jsonupdated if new parameters are added.What kind of change does this PR introduce?
Adds a
closefeature to the gRPCMonitorcall. This new feature allows the client to gracefully close the port monitor.What is the current behavior?
To close a gRPC-opened monitor, the client must close the gRPC streaming call, BTW this creates a race condition: the client is not aware of when the connection to the port is actually closed by the daemon afterward.
See #2271 for details.
What is the new behavior?
The
closemessage should allow to gracefully close the monitor.Does this PR introduce a breaking change, and is titled accordingly?
Yes, the gRPC
Monitorcall has been refactored to use a better description of the gRPC message based on theoneofdescriptor.Other information
Fix #2271